Versions:
pxgo is an HTTP/HTTPS proxy developed and published by pavelsimo, currently available in version 0.4.0, which stands as the single release listed in its version history. The software is designed to solve a specific and common problem in enterprise environments: enabling local tools and services to communicate through corporate upstream proxies that require authentication. Its distinguishing capability is support for NTLM and Kerberos authentication, two authentication schemes frequently encountered in corporate networks, particularly those built around Microsoft-based infrastructure. By handling these authentication mechanisms on behalf of the applications that route traffic through it, pxgo allows tools that lack native support for NTLM or Kerberos to function correctly behind restrictive upstream proxies. The software is distributed as a single binary, which simplifies deployment since it requires no complex installation process, external dependencies, or elaborate runtime environment to operate. This packaging approach makes it practical to drop onto a wide range of machines with minimal setup effort. Its stated target environments include developer machines, build agents, and local services, reflecting a focus on individual workstations and automated continuous integration infrastructure rather than large-scale server deployments. In a typical use case, a developer working on a corporate network would run pxgo locally and point their tools, package managers, or other HTTP clients at it, while pxgo manages the authenticated connection to the upstream corporate proxy. Similarly, build agents that must download dependencies or push artifacts through an authenticated proxy can route their traffic through pxgo to satisfy authentication requirements without modification to the build tooling itself. As a category, pxgo falls within networking and proxy software, specifically developer-oriented proxy tooling for authenticated corporate environments. At version 0.4.0, with only one recorded version, the project remains in an early stage of its release lifecycle, and prospective users should evaluate it with that maturity level in mind when considering adoption for their workflows.
Tags: